Docker engine daemon
To configure docker engine daemon, edit the file /etc/systemd/system/docker.service.d/docker.conf (if it does not exist, create folder docker.service.d and file docker.conf inside it).
[Service]
ExecStart=
ExecStart=/usr/bin/dockerd --config-file /etc/docker/daemon.json
ExecStartPost=
ExecStartPost=/usr/sbin/conntrack -F
ExecStart=
ExecStart=/usr/bin/dockerd --config-file /etc/docker/daemon.json
ExecStartPost=
ExecStartPost=/usr/sbin/conntrack -F
Then edit /etc/docker/daemon.json (if it does not exist, create the folders and file).
{
"bip": "192.168.13.1/24",
"hosts": [
"unix:///var/run/docker.sock",
"tcp://0.0.0.0:2376"
],
"insecure-registries": [
"livesp-registry.liveaction.com:5000"
] ,
"tlscacert": "/etc/docker/certs/ca.pem",
"tlscert": "/etc/docker/certs/server-cert.pem",
"tlskey": "/etc/docker/certs/server-key.pem",
"tlsverify": true
}
"bip": "192.168.13.1/24",
"hosts": [
"unix:///var/run/docker.sock",
"tcp://0.0.0.0:2376"
],
"insecure-registries": [
"livesp-registry.liveaction.com:5000"
] ,
"tlscacert": "/etc/docker/certs/ca.pem",
"tlscert": "/etc/docker/certs/server-cert.pem",
"tlskey": "/etc/docker/certs/server-key.pem",
"tlsverify": true
}
IMPORTANT: You have to change the private IP range (192.168.13.1/24) in the bip parameter to any other private IP range if you are already using this in your network architecture.